Media storage for online meetings in edge network storage

ABSTRACT

Disclosed in some examples are improved storage, replication, and distribution of data related to network-based meetings (e.g., media) in hierarchical records. Data for one or more components of the meeting (e.g., media) may be stored in a child record (called a component record). The network-based meeting may be described by a parent record with links to, and in some examples descriptions of, the meeting component records (the child records). The meeting object may point to local, and/or replicated copies of the child records. As noted, the child records may be or include media objects and, in some examples, the child records may be replicated to one or more locations based upon a demand for the media object. By replicating the media to a location that is close to demand for the media, this provides for more efficient delivery of media of the meeting.

TECHNICAL FIELD

Embodiments pertain to replication of hierarchical data. Someembodiments relate to efficient replication of hierarchical data. Someembodiments relate to efficient updates to replicated data. Someembodiments relate to storing and replication of network-based meetingdata and media.

BACKGROUND

Data may be replicated across one or more storage devices in one or moredata storage locations or regions. Replication may be performed for avariety of reasons. For example, replication may enhance dataavailability by storing multiple copies of the data in differentlocations. If one of the locations becomes unavailable or loses thedata, the data is still available in another location. In some otherexamples, privacy laws may require data generated in one location to bereplicated to another location. In still other examples, data ismigrated in order to create a backup copy of the data in case theprimary copy is lost or corrupted.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The drawings illustrate generally, by way of example, butnot by way of limitation, various embodiments discussed in the presentdocument.

FIG. 1 illustrates a schematic of a parent record and a correspondingchild record according to some examples of the present disclosure.

FIG. 2 illustrates a schematic of a data replication system replicatinga child record according to some examples of the present disclosure.

FIG. 3 illustrates a schematic of the data replication systemreplicating a parent record according to some examples of the presentdisclosure.

FIG. 4 illustrates a flowchart of a method of a replicator according tosome examples of the present disclosure.

FIG. 5 illustrates a flowchart of another method of a replicatoraccording to some examples of the present disclosure.

FIG. 6 illustrates a schematic diagram of a parent record with links toother parent records according to some examples of the presentdisclosure.

FIG. 7 illustrates a flowchart of a method of updating a parent and/orchild record according to some examples of the present disclosure.

FIG. 8 illustrates a flowchart of a method of replicating a parentrecord of a hierarchical record according to some examples of thepresent disclosure.

FIG. 9 illustrates a flowchart of a method of the operation of causingreplication of the first record according to some examples of thepresent disclosure.

FIG. 10 illustrates a flowchart of a method of the operation of causingreplication of the first record according to some examples of thepresent disclosure.

FIG. 11 illustrates a flowchart of a method of replicating a childrecord of a hierarchical record according to some examples of thepresent disclosure.

FIG. 12 illustrates a flowchart of a method of replicating a childrecord of a hierarchical record according to some examples of thepresent disclosure.

FIG. 13 illustrates a flowchart of a method for propagating updates to areplicated hierarchical record according to some examples of the presentdisclosure.

FIG. 14 illustrates a logical diagram of a replicator according to someexamples of the present disclosure.

FIG. 15 illustrates a media delivery system of a network-based meetingusing replication according to some examples of the present disclosure.

FIG. 16 illustrates a flowchart of a method of replicating network-basedmeeting records based upon a media demand according to some examples ofthe present disclosure.

FIG. 17 illustrates a flowchart of a method for processing a request fora media item or other record of a network-based meeting.

FIG. 18 is a block diagram illustrating an example of a machine uponwhich one or more embodiments may be implemented.

DETAILED DESCRIPTION

Records may be flat-structured, in that they do not have links orreferences to other objects that also need to be replicated. In otherexamples, records may be hierarchical in that they have links to otherrecords that need to be replicated. The hierarchy may be a parent-childhierarchy in that a parent record includes references to a plurality ofchild records that may be distinct from the parent record. In someexamples, the parent record in a hierarchical record may also includelinks to local copies of its child records so the child records areeasily located.

Replication of flat structured records may be simple as these recordsmay be immediately replicated once they are available by copying them toanother storage device. Flat structured records may not be appropriatein certain circumstances, such as where the amount of data stored in therecord gets very large. In some examples, a hierarchical record may bemore manageable as each piece may be replicated individually.

On the other hand, when the records to be replicated are hierarchicalthere may be complications to efficient replication. For example, inorder to make finding pieces of hierarchical records easier, the recordsmay have links to other pieces. For example, a parent record may havelinks to a local copy of the child records. The complications come fromthe difficulty in properly updating the links in the parent record tothe child records given the possibility that parent records and childrecords may arrive out of order. For example, a parent record may becomeavailable for replication first before the child record becomesavailable. The replicated parent record needs to update its links to thechild records when the child records are later replicated. This presentsa book-keeping issue as the system then needs to periodically check todetermine whether the child records have been replicated. Similarly, ifthe child records are replicated first, then the system needs to have away of tracking the child record's location once the parent record isfinally replicated to update the links in the parent.

Prior art solutions typically delay replication of hierarchical recordsuntil the data center receives all the associated records. Forsituations where a parent record may have hundreds or thousands ofcorresponding child records, and where a system may have thousands ofrecords it needs to process, waiting to receive all records beforestarting replication is an enormous cost in terms of time and computingresources. For example, additional memory resources may be needed tostore and manage the thousands of records waiting on replication. Such asystem may also cause bursts of processing and network traffic once therecords are available as the system tries to process thousands ofrecords at once and send them for replication. This may stress networkand computing resources.

Furthermore, in cases in which the records may be updated at a futuredate, once these records are replicated, they may be replicated to manydifferent data storage regions. If there is a change to one of theserecords, these changes need to be replicated to all other regions.Finding the regions affected and performing this replication may be ascostly as the original replication.

Disclosed in some examples are methods, systems, and machine readablemediums for efficient asynchronous replication of hierarchical recordsacross data storage locations. In some examples of the disclosed system,child records may be replicated as they are received without waiting forthe parent records to be received and without waiting for other childrecords to be received. In other examples of the disclosed systems, bothparent and child records may be replicated as they are received. Thisprovides for faster replication of the hierarchical record. Methods andsystems are also described for efficiently updating replicated records.

Disclosed also in some examples are improved storage, replication, anddistribution of data related to network-based meetings (e.g., media) inhierarchical records. Data for one or more components of the meeting(e.g., media) may be stored in a child record (called a componentrecord). The network-based meeting may be described by a parent recordwith links to, and in some examples descriptions of, the meetingcomponent records (the child records). The meeting object may point tolocal, and/or replicated copies of the child records. As noted, thechild records may be or include media objects and, in some examples, thechild records may be replicated to one or more locations based upon ademand for the media object. By replicating the media to a location thatis close to demand for the media, this provides for more efficientdelivery of media of the meeting. The use of hierarchical records forstoring meeting information is more efficient as pieces of the meetingmay be stored in different locations and handled separately. This alsoallows the system to host larger network-based meetings.

As used herein, a hierarchical record may include a parent record andone or more child records of the parent. The replicator system mayprocess parent and child records asynchronously as they arrive. Uponreceiving either a parent or child record, the replicator mayautomatically identify the relationships between the parent and child.For example, upon receiving a parent record, the replicator system mayidentify metadata in the parent record identifying the child records. Insome examples, child records may also have information linking them tothe parent records (e.g., a parent identifier).

In some examples, the replication policy of the system may specifywhether parent records are to be replicated to each data storage regionto which a child was replicated to. In some examples, the replicationpolicy may also specify whether child records are cross replicated basedupon their relationships with sibling child records. That is, a firstchild record that is replicated to a first region and whether a siblingchild record is also replicated to the first region may be specified bythe replication policy (which may consider information in the siblingrecord along with the fact that the first child record was replicated).

In some examples, upon receiving a notification that child record isavailable for replication, the child record may be immediatelyreplicated regardless of the status of the replication of other childrecords or the parent record. The replicator system may utilizereplication information in the child record and a replication policy todetermine whether to replicate the child record to one or more differentdata storage regions. Example replication information may include ageographic location of a user associated with the record (e.g., therecord may describe a media connection between a user device of the userand a media server), a demand for media stored in the record, and thelike. The child record may then be replicated to the one or moredifferent data storage regions without waiting for other child recordsor the parent record. An entry may be created in an index serving theone or more different data storage regions recording an identifier ofthe replicated child record. This index record may be used to laterupdate the links to the child records within the parent record when itis replicated.

Upon receiving a notification that a parent record is available forreplication, if the parent record is to be replicated to each datastorage region that a child was replicated to, the system uses metadataof the child records within the parent record, in conjunction with areplication policy, to determine which data storage regions each childrecord was replicated to or is to be replicated to. Note that the parentrecord may become ready for replication before, during, or after thereplication of all the child records. As noted previously, in someexamples, the system waits until all child records are replicated beforereplicating the parent. To determine whether the child records have allbeen replicated, the replicator may use the unique identifier of eachchild record (obtained from the metadata in the parent record) to queryan index serving the data storage regions to which each child record isto be replicated. If, for a particular data storage region, the indexreturns a result for the unique identifier of the child record, thesystem may determine that the child record was successfully replicatedto that data storage region.

If all child records have been replicated to all data storage regions, acopy is made of the parent record and the copy is replicated to eachdata storage region. The copy of the parent record may have fieldsidentifying local locations of the child records. These fields may beupdated in the copy to refer to the replicated location based uponresults returned from the indices. If the child records are notreplicated, replication of the parent record may be delayed a specifiedamount of time. In examples in which the child records are all crossreplicated to each data storage region to which sibling child recordswere replicated to, once the parent record is ready for replication, thesystem may kick off replication of other child records not alreadyreplicated to each particular data storage region. In some examples, oneor more parent record copies may have information describing eachlocation where a copy of one or more parent and/or child records arereplicated for easily determining where records are located throughout astorage system.

As noted, in some examples, if the child records have not beencompletely replicated, the replicator may queue the processing of theparent document for a variable interval to allow for the replication ofthe child documents. For example, the interval may be set to a shortamount of time for the initial wait period and then be increased foreach subsequent wait period until the parent record is replicated. Insome examples, the interval timer may be set based upon the number ofchild records. For example, the more child records the longer theinterval timer. After the final interval, the replicator may determinethat a child record was lost and initiate replication of the parent.

In other examples, rather than wait for each child record to bereplicated, the parent may be replicated to each data storage regionimmediately. For example, the system may determine which data storageregions to replicate the parent based upon an analysis of the childinformation within the parent and the replication policy. In theseexamples, the child record may include a unique identifier of the parentrecord. Once the parent is replicated, upon receiving a subsequent childrecord, the replication system may replicate the child record to asecond data storage region. As part of the replication of the childrecord, the index servicing the second data storage region may bechecked to see if a parent identifier is present. If the parentidentifier is present, it indicates that the parent record was alreadyreplicated. If the parent record was already replicated, the link to thechild record in the replicated parent record may be updated. If theparent identifier is not present, it indicates that the parent recordhas not yet been replicated and thus no further action is needed.

This system solves the technical problem of efficient replication ofhierarchical data records by the technical solution of asynchronousreplication of child records independent of the replication of theparent record using metadata in the parent record and a data index. Insome examples, the parent records may also be asynchronously replicatedindependent of the child records. The disclosed techniques allow formore efficient replication of large collections of hierarchical recordsby bypassing the traditional delays caused by waiting for the entirehierarchical record to become available. This also saves memory thatwould otherwise be used to cache these records or used to save stateinformation while waiting for the record to be complete. Furthermore, insome examples, by not delaying the replication of the records until theentire hierarchical record is received, the replication system canschedule replication of the records at a convenient time (which maystill be before the receipt of the entire hierarchical record) whencomputing resources are available. Additionally, by allowing records tobe replicated upon arrival at the replication system, network andprocessor usage may be spread out over time, rather than being bursty.This improves the operation of the computer network between data storageregions as well as reduces the amount of peak processing power necessaryon the replication system.

Additionally, the disclosed techniques of using hierarchical records tostore data about and media from network-based meetings allows forincreased participation in these meetings without additionally requiringa massive increase in computational power to handle these meetings.Further, by utilizing the above replication scheme, the records storingmedia may be replicated to one or more data storage regions withcomputing resources near a (geographic or network) location that iscloser to a demand for this media. This allows for delivering this mediain a faster manner with less latency. This also reduces network trafficas it allows for a more direct route.

FIG. 1 illustrates a schematic of a parent record 105 and acorresponding child record 120 according to some examples of the presentdisclosure. Parent record 105 may be a parent record to one or morechild records, such as child record 120. Parent record 105 may have aset of one or more parent data fields 110. For example, if the parentrecord 105 is a record of a network-based meeting, parent data fields110 may include fields such as a meeting identifier; a start time; anend time; links to (or copies of) media shared before, during, and afterthe meeting; links to media that is a recording of the meeting; copiesof media; metrics of the communication quality; and the like. In someexamples, the parent data fields 110 may include a parent identifierthat uniquely identifies the parent record 105. Each parent record mayhave a set of one or more child metadata structures 112A, 112B-112N.Child metadata structures may include an identifier of the child 114, achild record version identifier 116, a child link 118 that links to alocal copy of the child (local to the data storage region that theparent record is stored at), and child replication information 121 whichmay be used, along with a replication policy to determine whether thechild should be replicated and where the child should be replicated to.Child replication information 121 is any information used to determine,alone, or in conjunction with other information (such as a replicationpolicy) whether, and/or where, to replicate the child record. In someexamples, the child replication information 121 may be a location, suchas a location of a user associated with the child record. In otherexamples, the child replication information 121 may be media informationrelated to a geographic demand for the media (e.g., which geographicregions are, or are likely to, request the media within the childrecord). In some examples, the demand may be a past demand; in otherexamples, the demand may be an anticipated demand based upon a locationof users attending or associated with the meeting. For example, if athreshold number of members of the meeting are in a particular location,one or more media files of the meeting may be replicated to thelocation.

In some examples, where the hierarchical record is for a network-basedmeeting, each child record may include information about eachparticipant's connection with a media server providing the meeting. Forexample, if there are twenty participants in the meeting, there would beone parent record and twenty child records. In these examples, the childreplication information may be a location of a user described by thechild record for the meeting.

Child record 120 may include the same fields as the child metadatastructures 112A-112N with values the same as the corresponding entry inthe parent record 105. For example, a child identifier field 122, childversion identifier 124, and child replication information 126. Inaddition, the child record 120 may have child data fields 132. In theexample of the network-based meeting, the child data fields 132 mayidentify the endpoints identifiers (e.g., the client and the mediaprocessor), may store or include quality metrics of the meeting, media,links to media, or the like. In examples in which both parent record 105and child record 120 can be asynchronously replicated, child record 120may also have parent information 130 that identifies or may be used toidentify the parent record 105, such as a unique identifier of theparent.

FIG. 2 illustrates a schematic 200 of a data replication systemreplicating a child record according to some examples of the presentdisclosure. The child record 210 is created and stored in data storage215 of a first data storage region, region A. The replicator 220identifies that child record 210 is ready for replication. For example,replicator 220 may monitor the data storage region A 215 for newrecords, or the data storage device or another process may notify thereplicator 220 of the creation of the child record 210. Replicator 220then determines, from the replication information (e.g., childreplication information 128) and a replication policy 217 whether thisrecord needs to be replicated and to which data storage regions. In theexample of FIG. 2, the replicator 220 determines that this record is tobe replicated to data storage region B.

Replicator 220 may cause the child record 210 to be replicated to thedata storage 230 in data storage region B without first receiving eitherthe parent record, or the complete record set, including sibling records(if any). Data storage 230 may include one or more data storage devices.Replicator 220 also causes the copy of the child record 210 stored inthe data storage 230 of data storage region B to be indexed in index240. For example, the child identifier may be used as a lookup value inthe index. The child identifier may be globally unique across the entiredata storage system.

As used herein, a data storage region comprises one or more data storagedevices or clusters in one or more logically grouped data centers. Insome examples, the logical grouping may be based upon a geographiclocation (e.g., a geographical region such as North America, Europe,South America, Asia, or the like) or based upon a physical or logicalposition of the data center or the components thereof in a networkstructure. Replicator 220 may be at data storage region A, data storageregion B, functions of replicator 220 may be performed at data storageregion A and data storage region B or may be in a different regionaltogether. In some examples, one or more components of FIG. 2 may be anedge server of a cloud platform.

FIG. 3 illustrates a schematic 300 of the data replication systemreplicating a parent record according to some examples of the presentdisclosure. In the example of FIG. 3, the parent record is replicated tothe same data storage regions as any child record. In FIG. 3, the systemalso waits for the child record to be replicated before replicating theparent record. The parent record 310 may be created and may be stored indata storage of a first data storage region (e.g., a data storage ofdata storage region A 215). Replicator 220 may identify that parentrecord 310 is available for replication. For example, replicator 220 maymonitor the data storage of data storage region A 215 for new records.In other examples, the data storage of data storage region A 215, orsome other process, may send a notification to replicator 220.

Replicator 220 may read the parent record 310 and in particular, readthe child metadata (such as child metadata structures 112A-112N) todetermine if any of the child records need to be replicated. If any ofthe child records need to be replicated, the replicator 220 maydetermine that the parent record (and all child records) also need to bereplicated to a different data storage region. That is, the parentrecord may be replicated to the same data storage regions to which thechild records are, or need to be, replicated to. Replicator 220 mayfirst determine whether all the child records are already replicated bydetermining if a record exists in the index 240 using the childidentifier in the child metadata of the parent record 310. If the childrecords are not already all replicated, replication of the parent record310 may be queued in the queue 330. Index 240 may serve one or more datastorage regions. As shown, the index 240 may serve data storage regionB.

Once all child records are replicated, a copy of parent record 310 iscreated 315 and the child links (e.g., child link 118) are updated topoint to the copy of each child record in the data storage 230 of datastorage region B as indicated by the index 240. Once the links to thechild records are updated, the replicator 220 causes the copy of parentrecord 315 to be replicated to the data storage 230 of data storageregion B and indexed into index 240.

Replicator 220 may be at data storage region A or data storage region B.In some examples, functions of replicator 220 may be performed at datastorage region A and data storage region B.

In the example of FIG. 3, the parent record has three child records,child x, y, and z. In examples in which the child records are eachreplicated (from an original data storage region) to different datastorage regions (e.g., first and second data storage regions) if thereplicator 220 identifies that a first child record is replicated to afirst data storage region and a second child record is replicated to asecond data storage region, then the replicator 220 may initiate areplication of the second child record to the first data storage regionand the second child record to the first data storage region. This mayhappen when the parent record is replicated. In other examples, thechild records replicated to other regions may not be cross replicated.That is, the first child record that was replicated to the first datastorage region may not be replicated to the second data storage regionand the second child record that was replicated to the second datastorage region may not be replicated to the first data storage region.In yet other examples, whether or not the child records are crossreplicated may be determined based upon the replication policy 217. Insome examples, one or more copies of the parent record 310 may beupdated to track all the locations to which the parent record, and/orone or more (or all) of the child records have been replicated to.

Replication policy 217 may be a set of one or more rules that mayutilize replication information, such as child replication information121, and in some examples, other information, to determine whether therecord is to be replicated and, if the record is to be replicated, towhich data storage regions the record is to be replicated. An examplereplication policy 217 may be to read the replication information fromone or more child records (e.g., child replication information 128) inthe record and determine from that information if, and where, the recordshould be replicated to. For example, this replication information maycomprise a location of a computing device that was a part of anetwork-based meeting described by the record. The replication policymay specify that the record is to be replicated to a data storage regionservicing that location. The replication policy may make use ofreplication information from a single child record, or multiple childrecords. In some examples, the replication information may be based uponone or more legal regulations such as a General Data ProtectionRegulation (GDPR), Health Insurance Portability and Accountability Act(HIPAA) or the like. In some examples, the replication policy mayrestrict replication such that a record that would otherwise bereplicated may not be replicated as a result of a replication policy(such as one based upon a legal obligation such as GDPR).

In yet other examples, replication information may include geographicdemand information of media stored within the record. For example, anactual geographic demand, an anticipated demand, or the like. Forexample, a location of users within the network-based meeting may beused to determine data storage regions that are likely to have a highvolume of access to the stored media (or contribute additional storedmedia after the meeting is over—such as for post meeting follow up).That is, the replication information may have location information ofmeeting participants and the replication policy may apply one or morethresholds (e.g., if a number of users for a particular region exceeds athreshold number, then the record is replicated to that region); or mayreplicate the record to the x regions with the greatest number of users(e.g., the x regions with the most users). In other examples, thereplication information may be a count of the number of actual accessesof the media based upon geographical region. The replication policy mayreplicate the record to one or more of the regions that access therecord the most. That is, the record may be replicated to a particularregion if it is accessed by a user within that region over a specifiedthreshold number of times. In other examples, the record may bereplicated to a top x number of regions based upon where the users thatmost access the record are located.

As noted, in some examples, if the child records are not already allreplicated, replication of the parent record may be queued in the queue330. The system will periodically pull the parent record from the queueand check to see if all the child records have been replicated. Once thechild records have all been replicated, the parent record is thenreplicated and the links to the child records in the replicated copy ofthe parent record are updated. A timer may be used to determine when tocheck the parent record in the queue to determine if the child recordsare all replicated. The timer may be specified and may be setup as atimer that progressively increases in length each time the parent recordis checked, and the system determines that the child records are not yetreplicated. For example, the first time may be set as one minute, thesecond check may be ten minutes, third check may be thirty minutes, anda fourth check may be sixty minutes. At a certain threshold number ofchecks, if the child records are not replicated, the system may declarean error and may give up or take some other action.

In other examples, if the child records are not already all replicated,the parent record may nonetheless be replicated to the data storage 230of data storage region B. An identifier of the parent record may beinserted into the index 240. In these examples, and turning back to FIG.2, upon replication of child records, the replicator 220 (which may bepresent at data storage region A, B. or some other region) may check theindex 240 for the parent identifier (that may be present in the childrecord 210). If the replicator 220 finds the parent record, thereplicator 220 may use the index to find the replicated copy in datastorage region B and update the child link to the location of thereplicated child record in data storage region B. Once all child recordsare replicated, all the links in the parent record for child recordsthat are to be replicated will be updated. If the replicator 220 doesnot find the parent identifier, then that means that the parent has notyet been replicated and the links will be updated once the replicator220 replicates the parent. In this manner, both parent and child recordsmay be replicated when they come in, whether the parent record is first,in the middle, or after the child records.

Turning now to FIG. 4, a flowchart of a method 400 of a replicator isshown according to some examples of the present disclosure. When a childrecord is created and identified by the replicator at operation 410, thereplicator determines whether to replicate the record at operation 420.In some examples this determination is made using a replication policyand one or more fields of the child record such as replicationinformation (such as location information). In examples in which thechild record is a component record of a network-based meeting, thereplication information may be a record of the location of a user endpoint of the meeting (e.g., based upon an IP address of a device used bythe user mapped to a location or based upon a GPS receiver in thedevice, or the like). If the determination is not to replicate the childrecord, then the flow ends. Other example replication information mayinclude media demand information.

Otherwise, if the child record is to be replicated, then at operation430, the replicator may cause the child record to be stored in one ormore data storage devices of one or more data storage regions determinedby operation 420. Causing the child record to be replicated may includesending the child record to a replicator executing at the data storageregion where the record is to be replicated. In other examples, causingthe child record to be replicated may include sending a notification toa replicator executing at the data storage region where the record is tobe replicated. The replicator executing at the data storage region wherethe record is to be replicated may then retrieve the record (e.g., fromthe data storage region that sent the notification).

At operation 435, one or more indexes are updated with entries for theoriginal and/or replicated copies. In some examples, the index may indexdata in a single data storage region. In these examples, each index foreach data storage region to which the child record is replicated may beupdated at operation 435. In other examples, a single index may indexdata for multiple data storage regions. In these examples, the singleindex may be updated for all replicated copies. In still other examplesmultiple indexes may each index data for all data storage regions. Thesystem may determine at operation 435 which indexes serve the regions towhich the child record was replicated and appropriately index the childrecord in those indexes. In some examples, updating the index is done bymessaging an indexing process on the index. In other examples, theindexing process may automatically determine that the child record wasadded through scanning of one or more data storage devices on the datastorage region.

When a parent record is ready for replication by the replicator atoperation 415, the replicator then decides whether to replicate theparent at operation 425. The replication may be made based upon areplication policy and based upon one or more fields in the parentrecord and/or one or child records (e.g., the replication information ofthe child records). In some examples, the parent may be replicated tothe same data storage regions as one or more of the child records. Ifthe parent record is not to be replicated, the flow may end. If theparent record is to be replicated, then at operation 445 a determinationis made as to whether all the child records are already replicated. Thisdetermination may be made based upon determining that all child recordsto be replicated to that storage region have associated index entries inthe data storage regions to which the child is supposed to bereplicated. If not, then the system may queue the replication of theparent record until all the child records are replicated, or until atimer expires. If the timer expires, the system may reset the timer (butwith a larger value) and wait for an additional interval. This mayhappen a specified number of times for a number of timer values untilthe system either gives up and labels the missing child record lost ortriggers a manual replication of the child records that have not yetbeen replicated.

At operation 455, for each location to which the parent is to bereplicated, a copy of the parent record is created. The metadata foreach child record within the parent record may be updated to point tothe local copy of each child record (e.g., child link 118 of FIG. 1). Atoperation 460, the copy of the parent record may be caused to be storedto the data storage device in a remote data storage region. As notedwith respect to the child record, the parent record may be caused to bereplicated by sending the parent record to the remote data storageregion or may be caused to be replicated by sending a notice to theremote data storage region indicating that a record is ready forreplication.

Turning now to FIG. 5, a flowchart of another method 500 of a replicatoris shown according to some examples of the present disclosure. Themethod 500 allows for asynchronous replication of parent and childrecords as opposed to waiting for all child records to be replicated asin FIG. 4. When a child record is identified as ready for replication bythe replicator at operation 510, the replicator determines whether toreplicate the record at operation 520. In some examples thisdetermination is made using a replication policy and one or more fieldsof the child record such as replication information (such as locationinformation). In examples in which the child record is a componentrecord of a network-based meeting, the replication information may be arecord of the location of a meeting participant (e.g., based upon an IPaddress of a device used by the user or based upon a GPS receiver in thedevice, or the like). If the determination is not to replicate the childrecord, then the flow ends.

Otherwise, if the child record is to be replicated, then at operation530, the replicator may cause the child record to be stored in one ormore data storage devices of one or more data storage regions determinedby operation 520. Causing the child record to be replicated may includesending the child record to a replicator executing at the data storageregion where the record is to be replicated. In other examples, causingthe child record to be replicated may include sending a notification toa replicator executing at the data storage region where the record is tobe replicated. The replicator executing at the data storage region wherethe record is to be replicated may then retrieve the record (e.g., fromthe data storage region that sent the notification).

At operation 535, one or more indexes are updated with entries for thereplicated copies. In some examples, the index may index data in asingle data storage region. In these examples, each index for each datastorage region in which the child record is stored may be updated atoperation 535. In other examples, a single index may index data formultiple data storage regions. In these examples, the single index maybe updated for all replicated copies. In still other examples multipleindexes may each index data for all data storage regions. The system maydetermine at operation 535 which indexes serve the regions to which thechild record was replicated and appropriately index the child record inthose indexes.

At operation 537, the replicator process may determine if the parentrecord has already been replicated to one or more of the destinationdata storage regions identified at operation 520. For example, byutilizing an identifier of the parent record stored within the childrecord and consulting an index of the remote data storage region todetermine whether the identifier is present within the index. If theparent has already been replicated, then at operation 539, the copy ofthe parent record stored in the destination data storage regions whereit is replicated may be updated to change the links to the local copiesof the child records in those destination data storage regions. If theparent is not replicated, then the flow may end.

When a parent record is identified as ready to be replicated by thereplicator at operation 515, the replicator then decides whether toreplicate the parent at operation 525. The replication may be made basedupon a replication policy and based upon one or more fields in theparent record and/or child record (e.g., replication information). Forexample, the replication policy may be to replicate the data to datastorage regions servicing locations indicated by the replicationinformation within the parent record, or the indicated in replicationinformation in one or more child metadata records. As noted, in someexamples, the parent record may be replicated to each data storageregion that a child was replicated to.

If the parent record is not to be replicated, the flow may end. If theparent record is to be replicated, then at operation 545 a determinationis made as to whether any child records are already replicated. Thisdetermination may be made based upon determining whether child recordshave associated index entries in the data storage regions to which thechild is supposed to be replicated. If not, then the system may proceedto operation 560.

At operation 555, for each location to which the parent is to bereplicated, a copy of the parent record is created. The metadata forchild records within the parent record that have already been replicatedmay be updated to point to the local copy of each child record. Atoperation 560, the copy of the parent record may be caused to be storedto the data storage device in a remote data storage region. As notedwith respect to the child record, the parent record may be caused to bereplicated by sending the parent record to the remote data storageregion or may be caused to be replicated by sending a notice to theremote data storage region indicating that a record is ready forreplication.

In some examples, one or more of the parent and/or child records mayneed to be updated after replication. For example, data may change inone or more fields for either the parent and/or the child. In otherexamples, additional child records may be added. Such changes may needto be replicated to other copies of the parent and/or child datastructures. In these examples, the changes may be replicatedasynchronously. For example, updated parent and/or child records may bereplicated as previously described. The updated records may be stored inaddition to, or may replace, the old records.

In still other examples, in order to update the records moreefficiently, a parent record may have links to the other parent recordswithin other data storage devices of other data storage regions. Thisallows the replicator to quickly locate the other records to updatethose records when a change to the record is identified.

FIG. 6 illustrates a schematic diagram 600 of a parent record with linksto other parent records according to some examples of the presentdisclosure. As with other examples, the parent records have metadatathat provides a location of child records within the data storageregion. For example, parent record 610, which is stored on a datastorage device of data region A 605, may have a parent record copy 612stored on a data storage device of data storage region B 615 that wasreplicated from the data storage region A 605. Parent record 610 mayhave metadata for each child record, including a child locator thatpoints to a local (e.g., within a same data storage region) location ofeach child record. For example, child record X locator 620 may point toone or more locations on one or more data storage devices in datastorage region A on which the child record X 630 is located. Similarly,child record Y locator 622 may point to one or more locations on one ormore data storage devices in data storage region A on which the childrecord Y 632 is located. Finally, child record Z locator 624 may pointto one or more locations on one or more data storage devices in datastorage region A on which the child record Z 634 is located.

Similarly, the parent record copy 612 stored on one or more storagedevices of data storage region B 615 may have metadata describing one ormore child documents. For example, child record X locator 636 may pointto one or more locations on one or more data storage devices in datastorage region B on which the child record X 652 is located. Similarly,child record Y locator 638 may point to one or more locations on one ormore data storage devices in data storage region B on which the childrecord Y 654 is located. Finally, child record Z locator 640 may pointto one or more locations on one or more data storage devices in datastorage region B on which the child record Z 656 is located.

In some examples, if a change to parent record copy 612 is detected atdata storage region A. 605; or data storage region B, 615; thereplicator (which may be at either or both of the data storage regions)may individually examine the child metadata in the parent record inconjunction with the data replication policy to determine which datastorage regions the parent record copy 612 and child records 630, 632,and 634 were replicated to. The replicator may then replicate anychanges to those data storage regions.

In other examples, when a parent record is replicated to another datastorage region, links to each data storage region that has a replicatedcopy may be created within one or more copies of the parent record(including the original parent record). For example, the parent record610 and the parent record copy 612 may have links to each other in thereplicated copy locators 626 and 650. This enables updates received ateither the data storage region A 605 or the data storage region B 615 tobe replicated to the other data storage regions quickly without havingto investigate the metadata of the child records. The replicated copylocator 626 may contain a link to each copy of the parent record in oneor more data storage regions. In FIG. 6, there are two copies—theoriginal parent record 610 and the parent record copy 612 and thus, thereplicated copy locator 626 points to the parent record copy 612 and thereplicated copy locator 650 points to parent record 610. In otherexamples, where there are more than two copies, multiple replicated copylocators may be stored within each copy of the parent record, each ofthe replicated copy locators points to a different copy in a differentdata storage region. Thus, if there are three copies of the parentrecord, there may be two replicated copy locators in each parent record.A first replicated copy locator points to a first copy, a secondreplicated copy locator points to a second copy.

FIG. 7 illustrates a flowchart of a method 700 of updating a parentand/or child record according to some examples of the presentdisclosure. At operation 705 if an update of a child record is received,then a corresponding parent record may be identified at operation 710.For example, by identifying the child identifier in the record andsearching for parent records with metadata with a matching childidentifier. In other examples, the child record may have an identifierof the parent. In still other examples, the parent record is not foundat operation 710 and flow proceeds directly to operation 720. The parentrecord may have information on other data storage regions to which therecords are replicated.

If an update of the parent record is received at operation 715, or oncethe corresponding parent record is identified (or the operation 710 isskipped), the record stored in the local region is updated at operation720. Similarly, for a child record, once the parent is updated, thelocal child record may be updated at operation 720. Operations 720, 730,and 745 apply whether the record is a parent or child record. Atoperation 730 the replicator may identify whether there are otherrecords stored in any other data storage regions. As noted, this may beperformed by identifying links to these other records in the parentrecord. In other examples, the replicator may examine the metadata ofthe child records and evaluate, based upon the replication policy,whether the data was replicated and to which regions. If there are noreplicated records, then the method 700 may terminate. If there areother replicated records, then the updates may be caused to be made tothe other copies at operation 745. For example, by sending a message tothe data storage regions requesting the update (which may include theupdate).

FIG. 8 illustrates a flowchart of a method 800 of replicating a parentrecord of a hierarchical record according to some examples of thepresent disclosure. At operation 805 the system may receive anindication that a first record is available for replication. Forexample, the system may receive the record from another device orcomponent (e.g., over a network) or may receive an indication that therecord was created and a replicator may then retrieve the record or aportion of the record (e.g., the metadata). At operation 810 thereplicator may determine whether the first record includes a descriptionof a second record such as a child record. That is, the replicator maydetermine if this record is a parent record of a hierarchical record.The description of the second record may include metadata includingchild replication information such as location data and a recordidentifier identifying the second record. The second record may be achild record of a first record.

If, at operation 815, the first record does not include a description ofone or more second records, then the flow may terminate. If, atoperation 815, the first record includes a description of one or moresecond records, then at operation 820, the system may determine, basedupon the replication information (e.g., geolocation data) in thedescription of the second record in the first record and a replicationpolicy whether the first record is to be replicated to a data storageregion.

If, at operation 825, the first record is not to be replicated, then themethod 800 may terminate. If, at operation 830, the first record is tobe replicated, then the system may cause replication of the first recordto the data storage region. In some examples, the method 800 isperformed in the data storage region or in a second data storage region.

FIG. 9 illustrates a flowchart of a method 900 of the operation ofcausing replication of the first record to the data storage regionaccording to some examples of the present disclosure. Method 900 may beone example method of operation 830 of FIG. 8. At operation 925, thereplicator may determine whether an index of the data storage regionindicates that the data storage region already has the second record. Ifnot, then the system may wait a specified amount of time. If atoperation 930, the data storage region already has the second record,then at operation 935 the system determines that the second record isalready replicated. At operation 940, the system may update, in a copyof the first record, a description of the second record to point tolocations of the second records in the data storage region. At operation945, the replicator may cause the copy of the first record to be storedin a data storage device of the data storage region.

FIG. 10 illustrates a flowchart of a method 1000 of the operation ofcausing replication of the first record to the data storage regionaccording to some examples of the present disclosure. Method 1000 may beone example implementation of operation 830 of FIG. 8. FIG. 10 differsfrom FIG. 9 in that the child records may include an identifier of theparent record and the parent record may be replicated independent of thechild record. The links to the child records in the parent record may beupdated once the parent record is replicated. At operation 1025, thereplicator may determine whether an index of the data storage regionindicates that the data storage region already has the second record(e.g., the child record). If not, then the method flow may proceed tooperation 1045. If at operation 1030, the data storage region alreadyhas the second record, then at operation 1035 the system determines thatthe second record is already replicated. At operation 1040, the systemmay update, in a copy of the first record, a description of the secondrecord to point to locations of the second records in the data storageregion. At operation 1045, the replicator may cause the copy of thefirst record to be stored in a data storage device of the data storageregion. As previously noted, FIGS. 8-10 may be performed by the datastorage region, a second data storage region, or partially at the datastorage region or the second data storage region.

FIG. 11 illustrates a flowchart of a method 1100 of replicating a childrecord of a hierarchical record according to some examples of thepresent disclosure. At operation 1105, the system may receive anindication that a child record is available for replication. Forexample, the system may receive the record from another device orcomponent (e.g., over a network) or may be receive an indication thatthe record was created and the replicator may then retrieve the recordor a portion of the record (e.g., the metadata).

At operation 1110, the system may determine whether the child record isto be replicated and if so, the replicator determines the data storageregions to which the child record is to be replicated. This may beaccomplished using the child replication information in the child datastructure and the replication policy. If the child record is not to bereplicated, then the method 1100 may terminate. If the child record isto be replicated, then at operation 1130, the replicator may causereplication of the child record to the indicated data storage region(s).For example, by copying the record to one or more data storage devicesof the data storage region(s). In other examples, the replicator maynotify one or more components of the data storage region(s) to copy therecord. At operation 1120, the replicator may cause an index to beupdated that indexes records for the data storage region(s) to index thereplicated copy of the record.

FIG. 12 illustrates a flowchart of a method 1200 of replicating a childrecord of a hierarchical record according to some examples of thepresent disclosure. FIG. 12 allows for replication of the parentseparately from the child record and includes additional checks to seeif the parent record was replicated and if so, to update the replicatedcopy of the parent record. At operation 1205, the system may receive anindication that a child record is available for replication. Forexample, the system may receive the record from another device orcomponent (e.g., over a network) or may be receive an indication thatthe record was created and the replicator may then retrieve the recordor a portion of the record (e.g., the metadata). In some examples, aspart of operation 1205, to determine that the record is a child record,the system may determine that the record includes a description of theparent record (e.g., an identifier of the parent record or some otherindicia that this is a child record).

At operation 1210, the system may determine whether the child record isto be replicated and if so, the replicator determines the data storageregion(s) to which the child record is to be replicated. This may beaccomplished using the child replication information in the child datastructure and the replication policy. If the child record is not to bereplicated, then the method 1200 may terminate. If the child record isto be replicated, then at operation 1230, the replicator may causereplication of the child record to the indicated data storage region(s).For example, by copying the record to one or more data storage devicesof the data storage region(s). In other examples, the replicator maynotify one or more components of the data storage region(s) to copy therecord. At operation 1235, the replicator may cause an index for thedata storage region(s) to be updated to index the replicated copy of therecord.

At operation 1240, the replicator may determine whether the parentrecord has been replicated. For example, by using an index of the datastorage region(s) and an identifier of the parent. The identifier of theparent may be stored in the child record or may be looked up bysearching for a corresponding parent record that has metadataidentifying the child record. If there is no record for the parentrecord in the index, then the parent record is not already replicated,and flow may terminate. If there is a record for the parent, then theparent was replicated first and at operation 1245, the replicator maycause the replicated copy of the parent stored in the data storageregion(s) to be updated with the location of the child record in thedata storage region(s). FIGS. 11 and 12 may be performed by the datastorage region, a second data storage region, or partially at the datastorage region or the second data storage region.

In some examples, replicating the parent first prior to the childrecords may cause issues if not all child records are replicated. Thatis, the links in a replicated parent record to the child records thathave not been replicated may be incorrect. In some examples, prior toreplication of the parent, all the child records that are not yetpresent in the data storage region(s) may be set to a value indicatingthat they are not yet replicated. In some examples, a timer may also bestarted. Upon replication of the last child record—which may bedetermined by checking to see if all child links have valid values, thetimer may be reset. If the timer expires, the system may act to eitherinitiate replication of the child records that were not replicated ordeclare an error condition.

In some examples, not all child records of a same parent record arereplicated to all data storage regions. That is, if a parent record hastwo child records, and the replication policy states that the firstchild record is to be replicated to a first data storage region and thesecond child record is to be replicated to the second data storageregion, then the parent record may be replicated to both the first andsecond data storage regions. The first child record may be replicated tothe first data storage region but not the second data storage region andthe second child record may be replicated to the second data storageregion but not the first data storage region. In other examples, othercombinations may be possible (e.g., the first child record may bereplicated to both regions, but the second child record is not). Inorder to handle these scenarios, not having a valid link to a local copyof the child record in the parent data structure may not produce anerror condition and may be normal. In still other examples, in thesecases, a special value may indicate that a particular child record waspurposefully not replicated.

FIG. 13 illustrates a flowchart of a method 1300 for propagating updatesto a replicated hierarchical record according to some examples of thepresent disclosure. At operation 1305, the replicator may receive anupdate indication. The update may specify one or more changes to therecord (either a parent or child record), or may be a new record toreplace the old record. At operation 1310, the system may update thelocal copy of the record (if this has not already been done). Atoperation 1315 the system may determine whether the record wasreplicated to one or more other data storage regions. If the record is achild record, this may be determined based upon the child replicationinformation in the child record. In examples in which the child recordmay be replicated to other data storage regions because of childreplication information of sibling records, the replicator may determineother data storage regions by locating the parent record and then usingthe child metadata and the replication policy of the parent record todetermine all replication locations. For parent records, the replicationpolicy and the replication locations may be used to determine thereplication locations. In other examples, links to other replicatedcopies may be used (e.g., replicated copy locator 626 and 650 of FIG.6). For example, the parent record of a child may be determined and theparent record may have links to child records. If there are noreplications, then the method 1300 may end. At operation 1320, thereplicated copies identified at operation 1315 may be updated.

Certain regulations in certain geographic regions may allow individualsto have access to, or delete, data describing them or their activities.For example, the European Union's General Data Protection Regulation(GDPR). The data structure described herein allows for easily tracingdata across one or more data storage regions. In some examples, theparent record data fields (e.g., parent data fields 110) may have aunique identifier of one or more users. In some examples, where thechild records are user specific, the child metadata structure 112A mayhave user identifiers for easy access. When a user desires to see dataabout them, the user's identifier is used to select parent recordscorresponding to the user. The child metadata in the parent records andthe replication policy may be used to easily find data storage regionsthat both the parents and their children were replicated to. This datamay then be obtaining for viewing, modified, or deleted from the datastorage regions.

In the case of a network-based meeting, the parent record 105 may storeidentifiers of all participants in the parent data fields 110. Instead,or additionally, in other examples, each component (child) metadatastructure 112A may have the identifier of the participant of thatcomponent (e.g., a connection to a media server for a real-timecommunication component of the meeting) as part of the metadata. Thus,the replicator can find the parent records associated with a particularuser identifier by searching the parent record (either the parent datafields or the child metadata, or both). Once the parent record islocated, the parent record's links to the child records may be used tofind all child records in all locations.

When the hierarchical records represent network-based meetings thesecommunications (e.g., network-based meeting) may be treated as anobject. For example, the parent record may be a group object such as ameeting object and the child structures may be components of the meetingsuch as media (such as media shared before, during, and after themeeting; and/or audio, video, or audiovideo of the meeting), connectionsbetween users and a media server for each participant in the meeting (asession record), and the like. As noted, the parent and/or childdocuments may store metadata about the meeting such as quality metrics,and the like. Additionally, or instead of this metadata, shareddocuments, videos (including those captured of participants), notes,virtual whiteboard drawings, chat sessions, and other meeting media maybe stored within the hierarchical record. For example, within theparent, child, or a combination of the parent and/or child records. Forexample, audio of a participant may be stored within a child record.Similarly, shared documents, and the like may be stored either in theparent object or within each child document.

Use of the hierarchical structure along with the replication schemedescribed herein may promote sharing and collaboration betweenparticipants, while still complying with privacy laws. For example, itallows replication of records that have shared media across differentdata storage regions so that users may access them quickly as the sharedmedia may be stored in a local data storage region. As noted, recordsincluding media may be replicated to geographic regions that have, orare expected to have high demand to view or play this media. Despitethis, the ability to update, locate, and modify the records in a quickand efficient manner allows for easier compliance with privacyregulations. Furthermore, by using the disclosed techniques to replicatethe hierarchical records more efficiently, these records may comply withdata privacy regulations with low impact to computing resources. In someexamples, the replication policy may specify one or more privacyregulations that prohibit, require, or allow replication to one or moredata storage regions.

FIG. 14 illustrates a logical diagram of a replicator according to someexamples of the present disclosure. Replicator 1400 may be an example ofreplicator 220 and may perform the flows and methods of FIGS. 2-13.Replicator 1400 may have a policy evaluator component 1410 which maydetermine an applicable replication policy (e.g., from a list ofreplication policies). The system may have multiple replication policiesthat have applicability rules that may specify which data structures thereplication policy applies to. In other examples, the applicabilityrules may also factor in child replication information when evaluatingwhether a particular policy is applicable. The one or more replicationpolicies may have one or more criteria that determine, based upon thechild replication information and/or other information, whether a recordis to be replicated and where. The replication rules may specifywhether, given the child replication information of all child records,certain child records, or other information in either the parent recordsor child records whether all child records are replicated or whetheronly certain child records are replicated. As noted, the childreplication information may be a geolocation or media usage data.

In some examples, the replication rules may be implemented as“if-then-else” statements which compare the values of the childreplication information and/or other data stored within the parentrecord and/or child records to values. For example, “if <the childrecord has a location X in the child replication information> then<replicate only that child record to data storage region for locationX>” As another example “if <the child record has a location X in thechild replication information> then <replicate the child record andparent record to data storage region for location X>” As yet anotherexample: “<the child record has a location X in the child replicationinformation> then <replicate the parent and all child records to datastorage region for location X>” This policy may be implemented using aprocessor, such as processor 1802 by configuring the processor usinginstructions (such as instructions 1824).

Index query component 1415 may query an index servicing a data storageregion to determine if one or more records are present in the index andmay also insert one or more records into one or more indices as a resultof replication of one or more records to record the presence of thereplicated record in the data storage of one or more data storageregions. Index query component 1415 may implement one or moreApplication Programming Interfaces (APIs) to query the index. Forexample, a Structured Query Language (SQL), Simple Object AccessProtocol (SOAP), or the like. Index query component 1415 may beimplemented by a processor, such as processor 1802 by configuring theprocessor using instructions (such as instructions 1824). Index querycomponent 1415 may communicate with the index using a network interface,such as network interface device 1820.

Record copier 1420 may create one or more copies of parent and/or childrecords in working memory (e.g., main memory 1504) and/or storage device(e.g., drive unit 1516) of the replicator for replication. Recordmodifier 1430 may update the location of the child records in a copy ofthe parent record to point to local copies within the data storageregion where the copy is to be (or has been) replicated. The recordmodifier may be implemented by a processor, such as processor 1802 byconfiguring the processor using instructions (such as instructions1824).

Storage component 1425 may cause storage of one or more copies of therecord at one or more data storage regions. In some examples, this maybe storage at a data storage region where the replicator is located. Inother examples, this may be storage at a data storage region remote fromwhere the replicator is located. This may be accomplished using one ormore Application Programming Interfaces (APIs). For example, aStructured Query Language (SQL), Simple Object Access Protocol (SOAP),or the like. The record copier 1420 may be implemented by a processor,such as processor 1802 by configuring the processor using instructions(such as instructions 1824). The record copier 1420 may communicate withthe index using a network interface, such as network interface device1820.

As previously described the system may replicate records such that mediastored within those records is stored at a geographic or logical networklocation closer to where demand is for the media. Media may include arecording of a network-based meeting; items or files shared amongstparticipants before, during, or after the meeting; a transcript of themeeting; chat sessions associated with the meeting; and the like. Insome examples, a meeting object may store links to one or more childrecords that have media items from the meeting. In some examples, ameeting object may be stored in one storage region and have links to oneor more other storage regions that have child records. That is, theparent record may not be replicated along with the child record. In someexamples, the child records of a network-based meeting may be termedcomponent records and may store media, information and metrics aboutconnections between a user device and a media server during the meeting,and the like.

FIG. 15 illustrates a media delivery system 1500 of a network-basedmeeting using replication according to some examples of the presentdisclosure. Communication service 1505 may provide one or more networkbased meetings. A network-based meeting is a collaboration betweenmultiple users over a network that includes real-time communications andmay include pre, and post meeting communications, planning, and mediasharing. The real-time communications aspect allows for real-time (ornear-real time) audio and/or video communications as well as filesharing and text messaging, real-time chat, screen sharing, whiteboardsharing, and the like.

Communication service 1505 may manage one or more aspects of anetwork-based meeting including real-time communication aspects, premeeting, post meeting, and other aspects. Media server instances, suchas media server instance A 1525 and media server instance B 1530 may bean endpoint for one or more devices, such as participant computingdevice 1550 and participant computing device 1572 for real-timecommunication aspects of the network-based meeting. The media serverinstances may communicate with each other to provide real-timecommunications between participant computing devices, such asparticipant computing device 1572 and 1550 as well as file sharing,screen sharing, and other features.

Record creator 1527 may create one or more records of the network-basedmeeting. For example, a meeting object record 1545 and one or morecomponent records, such as component record A 1535, and component recordB 1540. For example, a component record may be created corresponding toa connection with a media server instance that records information aboutthe session such as call metrics, call quality, and the like. Inaddition, media may be stored within the component records. For example,a media file A may be stored within the component record A 1535.

Replicator 1520 may be an example of replicator 1400 according to someexamples of the present disclosure. Replicator 1520 may replicate one ormore of the records to data storage of one or more data storage regions,such as data storage 1560 of data storage region B 1510 or data storage1565 of data storage region A 1515. Media demand determiner 1532 maydetermine a demand for media of the network-based meeting. The demandmay be an actual demand—that is, a number of accesses or attemptedaccesses of a particular item of media. The demand may be a predicteddemand. The predicted demand may be based upon a number of usersauthorized to access the media and their locations. The record creator1527 may use the media demand to set the replication information in thevarious component records and/or the meeting object record.

Data storage region A 1515 and data storage region B 1510 may serviceone or more geographic or logical network regions that includeparticipant computing devices 1572, 1550; and other user computingdevices 1570, 1517, and 1555. Participant computing devices 1572, 1550are participants in a real-time communications portion of anetwork-based meeting. User computing devices 1570, 1517, and 1555 maynot be participants in the real-time communication portion, but may beotherwise authorized to access media and information about thenetwork-based meeting.

As shown in FIG. 15, the records 1535, 1540, and 1545 are all replicatedto data storage region A 1515. In some examples, this may be due to thepredicted demand for the media in data storage region A. For example,there are three computing devices (1572, 1517, and 1570) that areauthorized to access the media of the network-based meeting and only twodevices in data storage region B 1510.

When accessing media A, computing devices 1570, 1517, and 1572 mayaccess the media from data storage 1565 of data storage region A 1515.In some examples, the devices first request the media from thecommunication service 1505. In these examples, the communication service1505 may determine from the meeting object record 1545 stored at thecommunication service 1505 that the media was replicated to a datastorage region local to the computing devices 1570, 1572, 1517. Thecommunication service 1505 may then instruct these devices to obtain themedia from the data storage 1565.

For devices in other data storage regions, such as device 1555, thecommunication service 1505 may instruct them to obtain the media fromeither the communication service 1505 or from the data storage 1565 inthe data storage region A 1515. For example, the system may beconfigured such that certain data storage regions may obtain media fromother data storage regions or from the communication service. In otherexamples, the communication service 1505 may redirect a device within aparticular data storage region that does not have the media replicatedto it to a data storage device in a different data storage region if thecommunication server is busy (e.g., a service load exceeds a threshold).In still other examples, the system may randomly choose whether toobtain the media from the communication service or a different datastorage region where the media was replicated. Over time, the system maylearn through observation of file transfer speeds, a fastest way toaccess the media—whether it is through the communication service, orthrough a different data storage region and under which conditions. Forexample, at a first time, the communication service may be fastest, butin other circumstances a different data storage region may be fastest.

FIG. 16 illustrates a flowchart of a method 1600 of replicatingnetwork-based meeting records based upon a media demand according tosome examples of the present disclosure. At operation 1605, the system(e.g., a communication service) may create a first record for a firstcomponent of a network-based meeting. At operation 1610, the system(e.g., the communication service) may create a second record for asecond component of the network-based meeting. The first and secondrecords may be records describing connection information between one ormore devices and a media server; may describe or include media; and/orthe like.

At operation 1615 the system (e.g., the communication service) maycreate a meeting object record including links to the first and secondrecords. At operation 1620, the system may determine whether the firstrecord is to be replicated to a first data storage region based upon areplication policy and geographic usage data of a first media item thatis stored within the first record. In some examples, rather than being aseparate record, the record may be the media file.

In some examples, the replication policy may specify to which datastorage regions to replicate the first record based upon the geographicusage data. For example, the replication policy may specify that therecord be replicated to a top three geographic regions based upon actualusage. In other examples, the replication policy may specify that therecord be replicated to the three data storage regions with the greatestnumber of participants of a real-time communication component of anonline meeting. In still other examples, the replication policy mayspecify that the record be replicated to the three data storage regionswith the greatest number of users authorized to access the media item.

If the first record is not to be replicated the flow proceeds tooperation 1630. If the first record is to be replicated, then the firstrecord is caused to be replicated to data storage on the first datastorage region at operation 1625. For example, by sending the firstrecord to a replicator on the first data storage region or by sending anotification to a replicator on the first data storage region.

At operation 1630, the system may determine whether the second record isto be replicated to a second data storage region based upon areplication policy and geographic usage data of the second media item.In some examples, the replication policy may specify to which datastorage regions to replicate the first record based upon the geographicusage data. For example, the replication policy specify that the recordbe replicated to a top three geographic regions based upon actual usage.In other examples, the replication policy may specify that the record bereplicated to the three data storage regions with the greatest number ofparticipants of a real-time communication component of an onlinemeeting. In still other examples, the replication policy may specifythat the record be replicated to the three data storage regions with thegreatest number of users authorized to access the media item. The firstand second data storage regions may be different. That is, some media ofthe network-based meeting may be replicated to different regions.

If the second record is not to be replicated, then flow proceeds tooperation 1640. If the second record is to be replicated, then atoperation 1635, the second record may be replicated to the second region(e.g., in a same or similar fashion as the first record to the firstdata storage region).

In some examples, the meeting object record is also replicated to thefirst and/or second data storage regions. Whether the meeting objectrecord is replicated may be determined by the replication policy or bydesign choice. The original meeting object record and/or the replicatedmeeting object records may store information on what records associatedwith a particular meeting are replicated where.

At operation 1640, the meeting object record stored at the network-basedcommunication service may be updated to store links to the replicatedcopies of the first and/or second record (depending on which recordswere replicated). This record may be used by the network-basedcommunication service, or another device that may route requests formedia of the network-based meeting, to determine a source for requestedmedia as described in FIG. 17. As shown, the network-based communicationservice routes requests for media and stores the original records of thenetwork-based meeting, but in other examples, other components may alsoperform these tasks.

While the disclosed examples utilized media usage information, one ofordinary skill in the art with the benefit of the present disclosurewill appreciate that other usage information for other records, such ascall statistics, may also be utilized and the present methods andsystems are not limited to media and media demand, but may be applied toany type of data. Additionally, the parent, or group record, in theexample of FIG. 16 may or may not be replicated to one or more of thelocations of the child records. Furthermore, the parent record may havelinks to the locations of all the child records.

FIG. 17 illustrates a flowchart of a method 1700 for processing arequest for a media item or other record of a network-based meeting. Atoperation 1705, the system may receive a request (e.g., at anetwork-based service) a request for a first media item. In someexamples, the network-based service may authenticate the request. Atoperation 1710, the system may determine a location of the user devicerequesting the media. For example, by mapping an Internet Protocoladdress of the user device to a location. At operation 1715, the systemmay determine, from the meeting object record, a closes data storageregion to the user having the media replicated. At operation 1720, thesystem may cause the media to be delivered to the user from the datastorage region identified in operation 1715. In some examples, thenetwork-based meeting service may send a link to the user device and theuser device may then use the link to download the media; in otherexamples, the network-based meeting service may instruct the datastorage region selected at operation 1715 to send the media to the userdevice.

In some examples, where the media may be replicated to multiple datastorage regions, each user may be directed to a different region to getthe media based upon their user credentials or based upon system load.That is, some users in a same location may be directed to different datastorage regions depending on either or a combination of system loadand/or system configurations.

FIG. 18 illustrates a block diagram of an example machine 1800 uponwhich any one or more of the techniques (e.g., methodologies) discussedherein may perform. In alternative embodiments, the machine 1800 mayoperate as a standalone device or may be connected (e.g., networked) toother machines. In a networked deployment, the machine 1800 may operatein the capacity of a server machine, a client machine, or both inserver-client network environments. In an example, the machine 1800 mayact as a peer machine in peer-to-peer (P2P) (or other distributed)network environment. Machine 1800 may be configured to create and/orstore parent records (e.g., such as parent records 105, 310, 610, 612),child records (120, 315, 630, 632, 634, 652, 654, 656), and the like.Machine 1800 may implement the replicator, index, data storage, and thelike. For example, replicator 220, index 240, data storage for datastorage region A 215, data storage for data storage region B 230, queue330, and the like. Machine 1800 may implement the data flows, methods,systems, devices, and any of the components shown in FIGS. 1-17.

The machine 1800 may be in the form of a personal computer (PC), atablet PC, a set-top box (STB), a personal digital assistant (PDA), amobile telephone, a smart phone, a web appliance, a network router, aserver, a switch or bridge, or any machine capable of executinginstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines that individually or jointly execute a set (or multiple sets)of instructions to perform any one or more of the methodologiesdiscussed herein, such as cloud computing, software as a service (SaaS),other computer cluster configurations.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a machine readable medium. In an example, thesoftware, when executed by the underlying hardware of the module, causesthe hardware to perform the specified operations.

Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Softwaremay accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

Machine (e.g., computer system) 1800 may include a hardware processor1802 (e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 1804 and a static memory 1806, some or all of which maycommunicate with each other via an interlink (e.g., bus) 1808. Themachine 1800 may further include a display unit 1810, an alphanumericinput device 1812 (e.g., a keyboard), and a user interface (UI)navigation device 1814 (e.g., a mouse). In an example, the display unit1810, input device 1812 and UI navigation device 1814 may be a touchscreen display. The machine 1800 may additionally include a storagedevice (e.g., drive unit) 1816, a signal generation device 1818 (e.g., aspeaker), a network interface device 1820, and one or more sensors 1821,such as a global positioning system (GPS) sensor, compass,accelerometer, or other sensor. The machine 1800 may include an outputcontroller 1828, such as a serial (e.g., universal serial bus (USB),parallel, or other wired or wireless (e.g., infrared (IR), near fieldcommunication (NFC), etc.) connection to communicate or control one ormore peripheral devices (e.g., a printer, card reader, etc.).

The storage device 1816 may include a machine readable medium 1822 onwhich is stored one or more sets of data structures or instructions 1824(e.g., software) embodying or utilized by any one or more of thetechniques or functions described herein. The instructions 1824 may alsoreside, completely or at least partially, within the main memory 1804,within static memory 1806, or within the hardware processor 1802 duringexecution thereof by the machine 1800. In an example, one or anycombination of the hardware processor 1802, the main memory 1804, thestatic memory 1806, or the storage device 1816 may constitute machinereadable media.

While the machine readable medium 1822 is illustrated as a singlemedium, the term “machine readable medium” may include a single mediumor multiple media (e.g., a centralized or distributed database, and/orassociated caches and servers) configured to store the one or moreinstructions 1824.

The term “machine readable medium” may include any medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine 1800 and that cause the machine 1800 to perform any one ormore of the techniques of the present disclosure, or that is capable ofstoring, encoding or carrying data structures used by or associated withsuch instructions. Non-limiting machine readable medium examples mayinclude solid-state memories, and optical and magnetic media. Specificexamples of machine readable media may include: non-volatile memory,such as semiconductor memory devices (e.g., Electrically ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM)) and flash memory devices; magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; RandomAccess Memory (RAM); Solid State Drives (SSD); and CD-ROM and DVD-ROMdisks. In some examples, machine readable media may includenon-transitory machine readable media. In some examples, machinereadable media may include machine readable media that is not atransitory propagating signal.

The instructions 1824 may further be transmitted or received over acommunications network 1826 using a transmission medium via the networkinterface device 1820. The Machine 1800 may communicate with one or moreother machines utilizing any one of a number of transfer protocols(e.g., frame relay, internet protocol (IP), transmission controlprotocol (TCP), user datagram protocol (UDP), hypertext transferprotocol (HTTP), etc.). Example communication networks may include alocal area network (LAN), a wide area network (WAN), a packet datanetwork (e.g., the Internet), mobile telephone networks (e.g., cellularnetworks), Plain Old Telephone (POTS) networks, and wireless datanetworks (e.g., Institute of Electrical and Electronics Engineers (IEEE)802.11 family of standards known as Wi-Fi®. IEEE 802.16 family ofstandards known as WiMax®). IEEE 802.15.4 family of standards, a LongTerm Evolution (LTE) family of standards, a Universal MobileTelecommunications System (UMTS) family of standards, peer-to-peer (P2P)networks, among others. In an example, the network interface device 1820may include one or more physical jacks (e.g., Ethernet, coaxial, orphone jacks) or one or more antennas to connect to the communicationsnetwork 1826. In an example, the network interface device 1820 mayinclude a plurality of antennas to wirelessly communicate using at leastone of single-input multiple-output (SIMO), multiple-inputmultiple-output (MIMO), or multiple-input single-output (MISO)techniques. In some examples, the network interface device 1820 maywirelessly communicate using Multiple User MIMO techniques.

OTHER NOTES AND EXAMPLES

Example 1 is a device for asynchronous data replication ofhierarchically related records across data storage regions, the devicecomprising: a processor; a memory, storing instructions, which whenexecuted by the processor, causes the device to perform operationscomprising: receiving an indication that a first record is available forreplication; determining whether the first record includes, adescription of a second record, the description of the second recordincluding replication information for the second record and a recordidentifier identifying the second record, the second record a childrecord of the first record; responsive to determining that the firstrecord includes the description of the second record: determining, basedupon the replication information in the description of the second recordand a replication policy, whether the first record is to be replicatedto a data storage region; and responsive to determining that the firstrecord is to be replicated to the data storage region, causingreplication of the first record to the data storage region, thereplication comprising: determining whether an index of the data storageregion contains an entry with a field matching the record identifier ofthe second record; responsive to determining that the index contains theentry with the field matching the record identifier of the secondrecord, determining that the second record has already been replicatedto the data storage region; responsive to determining that the secondrecord has already been replicated to the data storage region, updatingthe description of the second record in a copy of the first record topoint to a location of the second record in the data storage region, thelocation stored in the index; and causing the copy of the first recordto be stored in data storage of the data storage region.

In Example 2, the subject matter of Example 1 includes, wherein thesecond record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a session identifieridentifying the communication session, and wherein the first record is agroup record describing a network-based meeting.

In Example 3, the subject matter of Example 2 includes, wherein thesecond record includes media shared during the network-based meeting.

In Example 4, the subject matter of Examples 1-3 includes, wherein theoperations further comprise: receiving an indication that the secondrecord is available for replication, the second record includingreplication information and a record identifier; determining, from thereplication information and the replication policy, whether to replicatethe second record to the data storage region; and responsive todetermining that the second record is to be replicated to the datastorage region, causing the second record to be stored in a data storageof the data storage region and the index to be updated with the recordidentifier and the location.

In Example 5, the subject matter of Example 4 includes, wherein theoperations further comprise: determining whether the first recordincludes a description of a third record, the description includingreplication information and a record identifier identifying the thirdrecord; responsive to determining that the first record includes thedescription of the third record, as part of the replication: determiningwhether the index of the data storage region contains a second entrywith a field matching a second record identifier of the third record;responsive to determining that the index contains the second entry withthe field matching the second record identifier of the third record,determining that the third record has already been replicated to thedata storage region; responsive to determining that the third record hasalready been replicated to the second data storage region, updating thedescription of the third record in the copy of the second record topoint to a second location of the third record in the second datastorage region, the second location stored in the index; and wherein thereplication of the second and third records is performed independently.

In Example 6, the subject matter of Examples 1-5 includes, wherein theoperations further comprise: responsive to determining that the indexdoes not contain the entry with the field matching the record identifierof the second record, waiting a prespecified amount of time; and whereinthe determining whether the index of the data storage region contains anentry with the field matching the record identifier of the secondrecord, the determining that the second record has already beenreplicated to the data storage region, the updating the description ofthe second record in a copy of the first record to point to a locationof the second record in the data storage region, the location stored inthe index and causing the copy of the first record to be stored in datastorage of the data storage region are performed after the prespecifiedamount of time has passed.

In Example 7, the subject matter of Examples 1-6 includes, wherein thereplication information of the second record comprises a geographicregion in which a user associated with the second record is located.

Example 8 is a method of asynchronous data replication of hierarchicallyrelated records across data storage regions, the method comprising:receiving an indication that a first record is available forreplication; determining whether the first record includes, adescription of a second record, the description of the second recordincluding replication information for the second record and a recordidentifier identifying the second record, the second record a childrecord of the first record; responsive to determining that the firstrecord includes the description of the second record; determining, basedupon the replication information in the description of the second recordand a replication policy, whether the first record is to be replicatedto a data storage region; and responsive to determining that the firstrecord is to be replicated to the data storage region, causingreplication of the first record to the data storage region, thereplication comprising: determining whether an index of the data storageregion contains an entry with a field matching the record identifier ofthe second record; responsive to determining that the index contains theentry with the field matching the record identifier of the secondrecord, determining that the second record has already been replicatedto the data storage region; responsive to determining that the secondrecord has already been replicated to the data storage region, updatingthe description of the second record in a copy of the first record topoint to a location of the second record in the data storage region, thelocation stored in the index; and causing the copy of the first recordto be stored in data storage of the data storage region.

In Example 9, the subject matter of Example 8 includes, wherein thesecond record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a session identifieridentifying the communication session, and wherein the first record is agroup record describing a network-based meeting.

In Example 10, the subject matter of Example 9 includes, wherein thesecond record includes media shared during the network-based meeting.

In Example 11, the subject matter of Examples 8-10 includes, receivingan indication that the second record is available for replication, thesecond record including replication information and a record identifier;determining, from the replication information and the replicationpolicy, whether to replicate the second record to the data storageregion; and responsive to determining that the second record is to bereplicated to the data storage region, causing the second record to bestored in a data storage of the data storage region and the index to beupdated with the record identifier and the location.

In Example 12, the subject matter of Example 11 includes, determiningwhether the first record includes a description of a third record, thedescription including replication information and a record identifieridentifying the third record; responsive to determining that the firstrecord includes the description of the third record, as part of thereplication; determining whether the index of the data storage regioncontains a second entry with a field matching a second record identifierof the third record; responsive to determining that the index containsthe second entry with the field matching the second record identifier ofthe third record, determining that the third record has already beenreplicated to the data storage region; responsive to determining thatthe third record has already been replicated to the second data storageregion, updating the description of the third record in the copy of thesecond record to point to a second location of the third record in thesecond data storage region, the second location stored in the index; andwherein the replication of the second and third records is performedindependently.

In Example 13, the subject matter of Examples 8-12 includes, responsiveto determining that the index does not contain the entry with the fieldmatching the record identifier of the second record, waiting aprespecified amount of time; and wherein the determining whether theindex of the data storage region contains an entry with the fieldmatching the record identifier of the second record, the determiningthat the second record has already been replicated to the data storageregion, the updating the description of the second record in a copy ofthe first record to point to a location of the second record in the datastorage region, the location stored in the index and causing the copy ofthe first record to be stored in data storage of the data storage regionare performed after the prespecified amount of time has passed.

In Example 14, the subject matter of Examples 8-13 includes, wherein thereplication information of the second record comprises a geographicregion in which a user associated with the second record is located.

Example 15 is a machine-readable medium storing instructions forasynchronous data replication of hierarchically related records acrossdata storage regions, the instructions, which when executed by amachine, causes the machine to perform operations comprising: receivingan indication that a first record is available for replication;determining whether the first record includes, a description of a secondrecord, the description of the second record including replicationinformation for the second record and a record identifier identifyingthe second record, the second record a child record of the first record;responsive to determining that the first record includes the descriptionof the second record: determining, based upon the replicationinformation in the description of the second record and a replicationpolicy, whether the first record is to be replicated to a data storageregion; and responsive to determining that the first record is to bereplicated to the data storage region, causing replication of the firstrecord to the data storage region, the replication comprising:determining whether an index of the data storage region contains anentry with a field matching the record identifier of the second record;responsive to determining that the index contains the entry with thefield matching the record identifier of the second record, determiningthat the second record has already been replicated to the data storageregion; responsive to determining that the second record has alreadybeen replicated to the data storage region, updating the description ofthe second record in a copy of the first record to point to a locationof the second record in the data storage region, the location stored inthe index; and causing the copy of the first record to be stored in datastorage of the data storage region.

In Example 16, the subject matter of Example 15 includes, wherein thesecond record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a session identifieridentifying the communication session, and wherein the first record is agroup record describing a network-based meeting.

In Example 17, the subject matter of Example 16 includes, wherein thesecond record includes media shared during the network-based meeting.

In Example 18, the subject matter of Examples 15-17 includes, whereinthe operations further comprise: receiving an indication that the secondrecord is available for replication, the second record includingreplication information and a record identifier; determining, from thereplication information and the replication policy, whether to replicatethe second record to the data storage region; and responsive todetermining that the second record is to be replicated to the datastorage region, causing the second record to be stored in a data storageof the data storage region and the index to be updated with the recordidentifier and the location.

In Example 19, the subject matter of Example 18 includes, wherein theoperations further comprise: determining whether the first recordincludes a description of a third record, the description includingreplication information and a record identifier identifying the thirdrecord; responsive to determining that the first record includes thedescription of the third record, as part of the replication: determiningwhether the index of the data storage region contains a second entrywith a field matching a second record identifier of the third record;responsive to determining that the index contains the second entry withthe field matching the second record identifier of the third record,determining that the third record has already been replicated to thedata storage region; responsive to determining that the third record hasalready been replicated to the second data storage region, updating thedescription of the third record in the copy of the second record topoint to a second location of the third record in the second datastorage region, the second location stored in the index; and wherein thereplication of the second and third records is performed independently.

In Example 20, the subject matter of Examples 15-19 includes, whereinthe operations further comprise: responsive to determining that theindex does not contain the entry with the field matching the recordidentifier of the second record, waiting a prespecified amount of time;and wherein the determining whether the index of the data storage regioncontains an entry with the field matching the record identifier of thesecond record, the determining that the second record has already beenreplicated to the data storage region, the updating the description ofthe second record in a copy of the first record to point to a locationof the second record in the data storage region, the location stored inthe index and causing the copy of the first record to be stored in datastorage of the data storage region are performed after the prespecifiedamount of time has passed.

In Example 21, the subject matter of Examples 15-20 includes, whereinthe replication information of the second record comprises a geographicregion in which a user associated with the second record is located.

Example 22 is a device asynchronous data replication of hierarchicallyrelated records across data storage regions, the device comprising:means for receiving an indication that a first record is available forreplication; means for determining whether the first record includes, adescription of a second record, the description of the second recordincluding replication information for the second record and a recordidentifier identifying the second record, the second record a childrecord of the first record; responsive to determining that the firstrecord includes the description of the second record; means fordetermining, based upon the replication information in the descriptionof the second record and a replication policy, whether the first recordis to be replicated to a data storage region; and means for, responsiveto determining that the first record is to be replicated to the datastorage region, causing replication of the first record to the datastorage region, the replication comprising: determining whether an indexof the second data storage region contains an entry with a fieldmatching the record identifier of the second record; responsive todetermining that the index contains the entry with the field matchingthe record identifier of the second record, determining that the secondrecord has already been replicated to the second data storage region;responsive to determining that the second record has already beenreplicated to the second data storage region, updating the descriptionof the second record in a copy of the first record to point to alocation of the second record in the second data storage region, thelocation stored in the index; and causing the copy of the first recordto be stored in data storage of the second data storage region.

In Example 23, the subject matter of Example 22 includes, wherein thesecond record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a session identifieridentifying the communication session, and wherein the first record is agroup record describing a network-based meeting.

In Example 24, the subject matter of Example 23 includes, wherein thesecond record includes media shared during the network-based meeting.

In Example 25, the subject matter of Examples 22-24 includes, means forreceiving an indication that the second record is available forreplication, the second record including replication information and arecord identifier; means for determining, from the replicationinformation and the replication policy, whether to replicate the secondrecord to the data storage region; and means for, responsive todetermining that the second record is to be replicated to the datastorage region, causing the second record to be stored in a data storageof the data storage region and the index to be updated with the recordidentifier and the location.

In Example 26, the subject matter of Example 25 includes, means fordetermining whether the first record includes a description of a thirdrecord, the description including replication information and a recordidentifier identifying the third record; means for, responsive todetermining that the first record includes the description of the thirdrecord, as part of the replication; determining whether the index of thedata storage region contains a second entry with a field matching asecond record identifier of the third record; responsive to determiningthat the index contains the second entry with the field matching thesecond record identifier of the third record, determining that the thirdrecord has already been replicated to the data storage region;responsive to determining that the third record has already beenreplicated to the second data storage region, updating the descriptionof the third record in the copy of the second record to point to asecond location of the third record in the second data storage region,the second location stored in the index; and wherein the replication ofthe second and third records is performed independently.

In Example 27, the subject matter of Examples 22-26 includes, means for,responsive to determining that the index does not contain the entry withthe field matching the record identifier of the second record, waiting aprespecified amount of time; and wherein the determining whether theindex of the data storage region contains an entry with the fieldmatching the record identifier of the second record, the determiningthat the second record has already been replicated to the data storageregion, the updating the description of the second record in a copy ofthe first record to point to a location of the second record in the datastorage region, the location stored in the index and causing the copy ofthe first record to be stored in data storage of the data storage regionare performed after the prespecified amount of time has passed.

In Example 28, the subject matter of Examples 22-27 includes, whereinthe replication information of the second record comprises a geographicregion in which a user associated with the second record is located.

Example 29 is a device for asynchronous data replication ofhierarchically related records across data storage regions, the devicecomprising: a processor; a memory, storing instructions, which whenexecuted by the processor, causes the device to perform operationscomprising: receiving, an indication that a first record is availablefor replication, the first record including replication informationassociated with the first record; determining whether the first recordincludes, a description of a second record, the second record a parentrecord of the first record; determining, based upon the replicationinformation in the first record and a replication policy, whether thefirst record is to be replicated to a data storage region; responsive todetermining that the first record is to be replicated to the datastorage region, causing replication of the first record to the datastorage region; determining whether an index of the data storage regioncontains an entry with a field matching a record identifier of thesecond record; responsive to determining that the index contains theentry with the field matching the record identifier of the secondrecord, determining that the second record has already been replicatedto the data storage region; and responsive to determining that thesecond record has already been replicated to the data storage region,updating, in a description of the second record, a pointer to a locationof the first record in the data storage region.

In Example 30, the subject matter of Example 29 includes, wherein thefirst record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a group identifieridentifying a network-based meeting, and wherein the second record is agroup record describing the network-based meeting.

In Example 31, the subject matter of Example 30 includes, wherein thefirst record includes media shared during the network-based meeting.

In Example 32, the subject matter of Examples 29-31 includes, whereinthe replication information is a geographic location of a user.

In Example 33, the subject matter of Examples 29-32 includes, whereinthe operations further comprise: receiving a second indication that athird record is available, the third record including replicationinformation associated with the third record; determining whether thethird record includes a description of a fourth record, the fourthrecord a parent record of the third record; determining, based upon thereplication information in the third record and a replication policy,whether the third record is to be replicated to the data storage region;responsive to determining that the third record is to be replicated tothe data storage region, causing replication of the third record to thedata storage region; determining whether an index of the second datastorage region contains an entry with a field matching the recordidentifier of the fourth record; and responsive to determining that theindex does not contain the entry with the field matching the recordidentifier of the fourth record, determining that the fourth record hasnot already been replicated to the data storage region.

In Example 34, the subject matter of Examples 29-33 includes, whereinthe indication that the first record is available comprises anindication that the first record was created, modified, is complete, oris ready for replication.

In Example 35, the subject matter of Examples 29-34 includes, whereinthe description of the second record comprises an identifier of thesecond record.

In Example 36, the subject matter of Examples 29-35 includes,determining that a third record is not to be replicated to the datastorage region based upon a replication policy.

In Example 37, the subject matter of Example 36 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 38 is a method of asynchronous data replication ofhierarchically related records across data storage regions, the methodcomprising: receiving, an indication that a first record is availablefor replication, the first record including replication informationassociated with the first record; determining whether the first recordincludes, a description of a second record, the second record a parentrecord of the first record; determining, based upon the replicationinformation in the first record and a replication policy, whether thefirst record is to be replicated to a data storage region; responsive todetermining that the first record is to be replicated to the datastorage region, causing replication of the first record to the datastorage region; determining whether an index of the data storage regioncontains an entry with a field matching a record identifier of thesecond record; responsive to determining that the index contains theentry with the field matching the record identifier of the secondrecord, determining that the second record has already been replicatedto the data storage region; and responsive to determining that thesecond record has already been replicated to the data storage region,updating, in a description of the second record, a pointer to a locationof the first record in the data storage region.

In Example 39, the subject matter of Example 38 includes, wherein thefirst record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a group identifieridentifying a network-based meeting, and wherein the second record is agroup record describing the network-based meeting.

In Example 40, the subject matter of Example 39 includes, wherein thefirst record includes media shared during the network-based meeting.

In Example 41, the subject matter of Examples 38-40 includes, whereinthe replication information is a geographic location of a user.

In Example 42, the subject matter of Examples 38-41 includes, receivinga second indication that a third record is available, the third recordincluding replication information associated with the third record;determining whether the third record includes a description of a fourthrecord, the fourth record a parent record of the third record;determining, based upon the replication information in the third recordand a replication policy, whether the third record is to be replicatedto the data storage region; responsive to determining that the thirdrecord is to be replicated to the data storage region, causingreplication of the third record to the data storage region; determiningwhether an index of the second data storage region contains an entrywith a field matching the record identifier of the fourth record; andresponsive to determining that the index does not contain the entry withthe field matching the record identifier of the fourth record,determining that the fourth record has not already been replicated tothe data storage region.

In Example 43, the subject matter of Examples 38-42 includes, whereinthe indication that the first record is available comprises anindication that the first record was created, modified, is complete, oris ready for replication.

In Example 44, the subject matter of Examples 38-43 includes, whereinthe description of the second record comprises an identifier of thesecond record.

In Example 45, the subject matter of Examples 38-44 includes,determining that a third record is not to be replicated to the datastorage region based upon a replication policy.

In Example 46, the subject matter of Example 45 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 47 is a machine-readable medium storing instructions forasynchronous data replication of hierarchically related records acrossdata storage regions, the instructions, which when executed by amachine, causes the machine to perform operations comprising: receiving,an indication that a first record is available for replication, thefirst record including replication information associated with the firstrecord; determining whether the first record includes, a description ofa second record, the second record a parent record of the first record;determining, based upon the replication information in the first recordand a replication policy, whether the first record is to be replicatedto a data storage region; responsive to determining that the firstrecord is to be replicated to the data storage region, causingreplication of the first record to the data storage region; determiningwhether an index of the data storage region contains an entry with afield matching a record identifier of the second record; responsive todetermining that the index contains the entry with the field matchingthe record identifier of the second record, determining that the secondrecord has already been replicated to the data storage region; andresponsive to determining that the second record has already beenreplicated to the data storage region, updating, in a description of thesecond record, a pointer to a location of the first record in the datastorage region.

In Example 48, the subject matter of Example 47 includes, wherein thefirst record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a group identifieridentifying a network-based meeting, and wherein the second record is agroup record describing the network-based meeting.

In Example 49, the subject matter of Example 48 includes, wherein thefirst record includes media shared during the network-based meeting.

In Example 50, the subject matter of Examples 47-49 includes, whereinthe replication information is a geographic location of a user.

In Example 51, the subject matter of Examples 47-50 includes, whereinthe operations further comprise: receiving a second indication that athird record is available, the third record including replicationinformation associated with the third record; determining whether thethird record includes a description of a fourth record, the fourthrecord a parent record of the third record; determining, based upon thereplication information in the third record and a replication policy,whether the third record is to be replicated to the data storage region;responsive to determining that the third record is to be replicated tothe data storage region, causing replication of the third record to thedata storage region; determining whether an index of the second datastorage region contains an entry with a field matching the recordidentifier of the fourth record; and responsive to determining that theindex does not contain the entry with the field matching the recordidentifier of the fourth record, determining that the fourth record hasnot already been replicated to the data storage region.

In Example 52, the subject matter of Examples 47-51 includes, whereinthe indication that the first record is available comprises anindication that the first record was created, modified, is complete, oris ready for replication.

In Example 53, the subject matter of Examples 47-52 includes, whereinthe description of the second record comprises an identifier of thesecond record.

In Example 54, the subject matter of Examples 47-53 includes,determining that a third record is not to be replicated to the datastorage region based upon a replication policy.

In Example 55, the subject matter of Example 54 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 56 is a device for asynchronous data replication ofhierarchically related records across data storage regions, the devicecomprising: means for receiving an indication that a first record isavailable for replication, the first record including replicationinformation associated with the first record; means for determiningwhether the first record includes, a description of a second record, thesecond record a parent record of the first record; means fordetermining, based upon the replication information in the first recordand a replication policy, whether the first record is to be replicatedto a data storage region; means for, responsive to determining that thefirst record is to be replicated to the data storage region, causingreplication of the first record to the data storage region; means fordetermining whether an index of the data storage region contains anentry with a field matching a record identifier of the second record;means for, responsive to determining that the index contains the entrywith the field matching the record identifier of the second record,determining that the second record has already been replicated to thedata storage region; and means for responsive to determining that thesecond record has already been replicated to the data storage region,updating, in a description of the second record, a pointer to a locationof the first record in the data storage region.

In Example 57, the subject matter of Example 56 includes, wherein thefirst record is a session record describing communications between acommunication application and a media controller of a communicationservice, and wherein the record identifier is a group identifieridentifying a network-based meeting, and wherein the second record is agroup record describing the network-based meeting.

In Example 58, the subject matter of Example 57 includes, wherein thefirst record includes media shared during the network-based meeting.

In Example 59, the subject matter of Examples 56-58 includes, whereinthe replication information is a geographic location of a user.

In Example 60, the subject matter of Examples 56-59 includes, whereinthe device further comprises: means for receiving a second indicationthat a third record is available, the third record including replicationinformation associated with the third record; means for determiningwhether the third record includes a description of a fourth record, thefourth record a parent record of the third record; means fordetermining, based upon the replication information in the third recordand a replication policy, whether the third record is to be replicatedto the data storage region; means for, responsive to determining thatthe third record is to be replicated to the data storage region, causingreplication of the third record to the data storage region; means fordetermining whether an index of the second data storage region containsan entry with a field matching the record identifier of the fourthrecord; and means for, responsive to determining that the index does notcontain the entry with the field matching the record identifier of thefourth record, determining that the fourth record has not already beenreplicated to the data storage region.

In Example 61, the subject matter of Examples 56-60 includes, whereinthe indication that the first record is available comprises anindication that the first record was created, modified, is complete, oris ready for replication.

In Example 62, the subject matter of Examples 56-61 includes, whereinthe description of the second record comprises an identifier of thesecond record.

In Example 63, the subject matter of Examples 56-62 includes, means fordetermining that a third record is not to be replicated to the datastorage region based upon a replication policy.

In Example 64, the subject matter of Example 63 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 65 is a device for distributing content of a network-basedmeeting, the device comprising: a processor; a memory, the memorystoring instructions, which when executed by the processor, cause thedevice to perform operations comprising: creating a first recorddescribing a first component of a network-based meeting and including afirst media item of the network-based meeting; creating a second recorddescribing a second component of the network-based meeting and includinga second media item of the network-based meeting; creating a meetingobject record, the meeting object record including links to the firstrecord and the second record and information about the first media itemand the second media item; determining whether the first record is to bereplicated to a data storage region based upon a replication policy andgeographical usage data of the first media item, the geographical usagedata stored in replication information of the first record, thegeographical usage data describing an actual or predicted demand of thefirst media item for a particular data storage region; responsive todetermining that the first record is to be replicated to the datastorage region, causing the first record to be replicated to the datastorage region; determining that the second record is to be replicatedto a second data storage region based upon the replication policy andgeographical usage data of the second media item stored in replicationinformation of the second record; responsive to determining that thesecond record is to be replicated to the second data storage region,causing the second record to be replicated to the second data storageregion; and storing, within the meeting object record, a link to thereplicated first record and the second record.

In Example 66, the subject matter of Example 65 includes, wherein theoperations further comprise: receiving at a network-based meetingservice, a request from a first user for the first media item;determining that the first user is within an area serviced by the datastorage region; determining from the meeting object record, a closestdata storage region to a user that has the media replicated, the closestdata storage region being the data storage region; and causingtransmission of the first media item to the first user from the datastorage region.

In Example 67, the subject matter of Examples 65-66 includes, whereinthe geographical usage data is a geographical location of participantcomputing devices of the network-based meeting.

In Example 68, the subject matter of Examples 65-67 includes, whereinthe geographical usage data is a geographical demand for the first andsecond media item.

In Example 69, the subject matter of Examples 65-68 includes, whereinthe media comprises audio of a conversation between a first and secondparticipant of the network-based meeting.

In Example 70, the subject matter of Examples 65-69 includes, whereinthe media comprises a file shared during the network-based meeting.

In Example 71, the subject matter of Examples 65-70 includes, whereinthe first record is stored on an edge server in the data storage region.

In Example 72, the subject matter of Examples 65-71 includes, whereinthe operations further comprise determining that the second record isnot to be replicated to the data storage region based upon a replicationpolicy.

In Example 73, the subject matter of Example 72 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 74 is a method for distributing content of a network-basedmeeting, the method comprising: creating a first record describing afirst component of a network-based meeting and including a first mediaitem of the network-based meeting; creating a second record describing asecond component of the network-based meeting and including a secondmedia item of the network-based meeting; creating a meeting objectrecord, the meeting object record including links to the first recordand the second record and information about the first media item and thesecond media item; determining whether the first record is to bereplicated to a data storage region based upon a replication policy andgeographical usage data of the first media item, the geographical usagedata stored in replication information of the first record, thegeographical usage data describing an actual or predicted demand of thefirst media item for a particular data storage region; responsive todetermining that the first record is to be replicated to the datastorage region, causing the first record to be replicated to the datastorage region; determining that the second record is to be replicatedto a second data storage region based upon the replication policy andgeographical usage data of the second media item stored in replicationinformation of the second record; responsive to determining that thesecond record is to be replicated to the second data storage region,causing the second record to be replicated to the second data storageregion; and storing, within the meeting object record, a link to thereplicated first record and the second record.

In Example 75, the subject matter of Example 74 includes, receiving at anetwork-based meeting service, a request from a first user for the firstmedia item; determining that the first user is within an area servicedby the data storage region; determining from the meeting object record,a closest data storage region to a user that has the media replicated,the closest data storage region being the data storage region; andcausing transmission of the first media item to the first user from thedata storage region.

In Example 76, the subject matter of Examples 74-75 includes, whereinthe geographical usage data is a geographical location of participantcomputing devices of the network-based meeting.

In Example 77, the subject matter of Examples 74-76 includes, whereinthe geographical usage data is a geographical demand for the first andsecond media item.

In Example 78, the subject matter of Examples 74-77 includes, whereinthe media comprises audio of a conversation between a first and secondparticipant of the network-based meeting.

In Example 79, the subject matter of Examples 74-78 includes, whereinthe media comprises a file shared during the network-based meeting.

In Example 80, the subject matter of Examples 74-79 includes, whereinthe first record is stored on an edge server in the data storage region.

In Example 81, the subject matter of Examples 74-80 includes,determining that the second record is not to be replicated to the datastorage region based upon a replication policy.

In Example 82, the subject matter of Example 81 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 83 is a machine-readable medium, storing instructions fordistributing content of a network-based meeting, the instructions, whenexecuted by a machine, cause the machine to perform operationscomprising: creating a first record describing a first component of anetwork-based meeting and including a first media item of thenetwork-based meeting; creating a second record describing a secondcomponent of the network-based meeting and including a second media itemof the network-based meeting; creating a meeting object record, themeeting object record including links to the first record and the secondrecord and information about the first media item and the second mediaitem; determining whether the first record is to be replicated to a datastorage region based upon a replication policy and geographical usagedata of the first media item, the geographical usage data stored inreplication information of the first record, the geographical usage datadescribing an actual or predicted demand of the first media item for aparticular data storage region; responsive to determining that the firstrecord is to be replicated to the data storage region, causing the firstrecord to be replicated to the data storage region; determining that thesecond record is to be replicated to a second data storage region basedupon the replication policy and geographical usage data of the secondmedia item stored in replication information of the second record;responsive to determining that the second record is to be replicated tothe second data storage region, causing the second record to bereplicated to the second data storage region; and storing, within themeeting object record, a link to the replicated first record and thesecond record.

In Example 84, the subject matter of Example 83 includes, wherein theoperations further comprise: receiving at a network-based meetingservice, a request from a first user for the first media item;determining that the first user is within an area serviced by the datastorage region; determining from the meeting object record, a closestdata storage region to a user that has the media replicated, the closestdata storage region being the data storage region; and causingtransmission of the first media item to the first user from the datastorage region.

In Example 85, the subject matter of Examples 83-84 includes, whereinthe geographical usage data is a geographical location of participantcomputing devices of the network-based meeting.

In Example 86, the subject matter of Examples 83-85 includes, whereinthe geographical usage data is a geographical demand for the first andsecond media item.

In Example 87, the subject matter of Examples 83-86 includes, whereinthe media comprises audio of a conversation between a first and secondparticipant of the network-based meeting.

In Example 88, the subject matter of Examples 83-87 includes, whereinthe media comprises a file shared during the network-based meeting.

In Example 89, the subject matter of Examples 83-88 includes, whereinthe first record is stored on an edge server in the data storage region.

In Example 90, the subject matter of Examples 83-89 includes, whereinthe operations further comprise determining that the second record isnot to be replicated to the data storage region based upon a replicationpolicy.

In Example 91, the subject matter of Example 90 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 92 is a device for distributing content of a network-basedmeeting, the device comprising: means for creating a first recorddescribing a first component of a network-based meeting and including afirst media item of the network-based meeting; means for creating asecond record describing a second component of the network-based meetingand including a second media item of the network-based meeting; meansfor creating a meeting object record, the meeting object recordincluding links to the first record and the second record andinformation about the first media item and the second media item; meansfor determining whether the first record is to be replicated to a datastorage region based upon a replication policy and geographical usagedata of the first media item, the geographical usage data stored inreplication information of the first record, the geographical usage datadescribing an actual or predicted demand of the first media item for aparticular data storage region; means for responsive to determining thatthe first record is to be replicated to the data storage region, causingthe first record to be replicated to the data storage region; means fordetermining that the second record is to be replicated to a second datastorage region based upon the replication policy and geographical usagedata of the second media item stored in replication information of thesecond record; means for, responsive to determining that the secondrecord is to be replicated to the second data storage region, causingthe second record to be replicated to the second data storage region;and means for storing, within the meeting object record, a link to thereplicated first record and the second record.

In Example 93, the subject matter of Example 92 includes, means forreceiving at a network-based meeting service, a request from a firstuser for the first media item; means for determining that the first useris within an area serviced by the data storage region; means fordetermining from the meeting object record, a closest data storageregion to a user that has the media replicated, the closest data storageregion being the data storage region; and means for causing transmissionof the first media item to the first user from the data storage region.

In Example 94, the subject matter of Examples 92-93 includes, whereinthe geographical usage data is a geographical location of participantcomputing devices of the network-based meeting.

In Example 95, the subject matter of Examples 92-94 includes, whereinthe geographical usage data is a geographical demand for the first andsecond media item.

In Example 96, the subject matter of Examples 92-95 includes, whereinthe media comprises audio of a conversation between a rust and secondparticipant of the network-based meeting.

In Example 97, the subject matter of Examples 92-96 includes, whereinthe media comprises a file shared during the network-based meeting.

In Example 98, the subject matter of Examples 92-97 includes, whereinthe first record is stored on an edge server in the data storage region.

In Example 99, the subject matter of Examples 92-98 includes,determining that the second record is not to be replicated to the datastorage region based upon a replication policy.

In Example 100, the subject matter of Example 99 includes, wherein thereplication policy comprises a replication policy based upon a privacylaw.

Example 101 is at least one machine-readable medium includinginstructions that, when executed by processing circuitry, cause theprocessing circuitry to perform operations to implement of any ofExamples 1-100.

Example 102 is an apparatus comprising means to implement of any ofExamples 1-100.

Example 103 is a system to implement of any of Examples 1-100.

Example 104 is a method to implement of any of Examples 1-100.

What is claimed is:
 1. A device for distributing content of anetwork-based meeting, the device comprising: a processor; a memory, thememory storing instructions, which when executed by the processor, causethe device to perform operations comprising: creating a first recorddescribing a first component of a network-based meeting and including afirst media item of the network-based meeting; creating a second recorddescribing a second component of the network-based meeting and includinga second media item of the network-based meeting; creating a meetingobject record, the meeting object record including links to the firstrecord and the second record and information about the first media itemand the second media item; determining whether the first record is to bereplicated to a data storage region based upon a replication policy andgeographical usage data of the first media item, the geographical usagedata stored in replication information of the first record, thegeographical usage data describing an actual or predicted demand of thefirst media item for a particular data storage region; responsive todetermining that the first record is to be replicated to the datastorage region, causing the first record to be replicated to the datastorage region; determining that the second record is to be replicatedto a second data storage region based upon the replication policy andgeographical usage data of the second media item stored in replicationinformation of the second record; responsive to determining that thesecond record is to be replicated to the second data storage region,causing the second record to be replicated to the second data storageregion; and storing, within the meeting object record, a link to thereplicated first record and the second record.
 2. The device of claim 1,wherein the operations further comprise: receiving at a network-basedmeeting service, a request from a first user for the first media item;determining that the first user is within an area serviced by the datastorage region; determining from the meeting object record, a closestdata storage region to a user that has the media replicated, the closestdata storage region being the data storage region; and causingtransmission of the first media item to the first user from the datastorage region.
 3. The device of claim 1, wherein the geographical usagedata is a geographical location of participant computing devices of thenetwork-based meeting.
 4. The device of claim 1, wherein thegeographical usage data is a geographical demand for the first andsecond media item.
 5. The device of claim 1, wherein the media comprisesaudio of a conversation between a first and second participant of thenetwork-based meeting.
 6. The device of claim 1, wherein the mediacomprises a file shared during the network-based meeting.
 7. The deviceof claim 1, wherein the first record is stored on an edge server in thedata storage region.
 8. The device of claim 1, wherein the operationsfurther comprise determining that the second record is not to bereplicated to the data storage region based upon a replication policy.9. The device of claim 8, wherein the replication policy comprises areplication policy based upon a privacy law.
 10. A method fordistributing content of a network-based meeting, the method comprising:creating a first record describing a first component of a network-basedmeeting and including a first media item of the network-based meeting;creating a second record describing a second component of thenetwork-based meeting and including a second media item of thenetwork-based meeting; creating a meeting object record, the meetingobject record including links to the first record and the second recordand information about the first media item and the second media item;determining whether the first record is to be replicated to a datastorage region based upon a replication policy and geographical usagedata of the first media item, the geographical usage data stored inreplication information of the first record, the geographical usage datadescribing an actual or predicted demand of the first media item for aparticular data storage region; responsive to determining that the firstrecord is to be replicated to the data storage region, causing the firstrecord to be replicated to the data storage region; determining that thesecond record is to be replicated to a second data storage region basedupon the replication policy and geographical usage data of the secondmedia item stored in replication information of the second record;responsive to determining that the second record is to be replicated tothe second data storage region, causing the second record to bereplicated to the second data storage region; and storing, within themeeting object record, a link to the replicated first record and thesecond record.
 11. The method of claim 10, further comprising: receivingat a network-based meeting service, a request from a first user for thefirst media item; determining that the first user is within an areaserviced by the data storage region; determining from the meeting objectrecord, a closest data storage region to a user that has the mediareplicated, the closest data storage region being the data storageregion; and causing transmission of the first media item to the firstuser from the data storage region.
 12. The method of claim 10, whereinthe geographical usage data is a geographical location of participantcomputing devices of the network-based meeting.
 13. The method of claim10, wherein the geographical usage data is a geographical demand for thefirst and second media item.
 14. The method of claim 10, wherein themedia comprises audio of a conversation between a first and secondparticipant of the network-based meeting.
 15. The method of claim 10,wherein the media comprises a file shared during the network-basedmeeting.
 16. The method of claim 10, wherein the first record is storedon an edge server in the data storage region.
 17. The method of claim10, further comprising determining that the second record is not to bereplicated to the data storage region based upon a replication policy.18. The method of claim 17, wherein the replication policy comprises areplication policy based upon a privacy law.
 19. A device fordistributing content of a network-based meeting, the device comprising:means for creating a first record describing a first component of anetwork-based meeting and including a first media item of thenetwork-based meeting; means for creating a second record describing asecond component of the network-based meeting and including a secondmedia item of the network-based meeting; means for creating a meetingobject record, the meeting object record including links to the firstrecord and the second record and information about the first media itemand the second media item; means for determining whether the firstrecord is to be replicated to a data storage region based upon areplication policy and geographical usage data of the first media item,the geographical usage data stored in replication information of thefirst record, the geographical usage data describing an actual orpredicted demand of the first media item for a particular data storageregion; means for responsive to determining that the first record is tobe replicated to the data storage region, causing the first record to bereplicated to the data storage region; means for determining that thesecond record is to be replicated to a second data storage region basedupon the replication policy and geographical usage data of the secondmedia item stored in replication information of the second record; meansfor, responsive to determining that the second record is to bereplicated to the second data storage region, causing the second recordto be replicated to the second data storage region; and means forstoring, within the meeting object record, a link to the replicatedfirst record and the second record.
 20. The device of claim 19, furthercomprising: means for receiving at a network-based meeting service, arequest from a first user for the first media item; means fordetermining that the first user is within an area serviced by the datastorage region; means for determining from the meeting object record, aclosest data storage region to a user that has the media replicated, theclosest data storage region being the data storage region; and means forcausing transmission of the first media item to the rust user from thedata storage region.